Vehicle detection systems and methods of operation thereof

ABSTRACT

A parking management system and methods of operation are disclosed. In one variation, a computer-implemented method comprises receiving positional data concerning a listing location from a listing client device; establishing a radius boundary based on the positional data; filtering one or more databases using the radius boundary to determine an amount of parking spaces listed and the amount of parking spaces reserved within a preset time period; calculating a location-specific transaction rate using the amount of parking spaces listed, the amount of parking spaces reserved, and the preset time period; determining a recommended listing price based on the location-specific transaction rate; and transmitting the recommended listing price to the listing client device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/571,166, filed Sep. 15, 2019, which is a continuation ofU.S. patent application Ser. No. 15/669,028, filed Aug. 4, 2017, nowissued as U.S. Pat. No. 10,438,488, which is a continuation of U.S.patent application Ser. No. 15/366,953, filed on Dec. 1, 2016, issued asU.S. Pat. No. 9,761,140, which is a continuation of PCT application No.PCT/US16/32529, filed on May 13, 2016, which claims the benefit of U.S.Provisional Application No. 62/162,574, filed on May 15, 2015.

All above-identified patents and patent applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

This disclosure relates generally to the field of vehicle parkingmanagement and, more specifically, to vehicle detection systems andmethods of operation thereof.

BACKGROUND

Parking a vehicle in densely populated environments is often afrustrating experience due to the dearth of free parking spaces and theexpense of private parking garages or lots. This is especially true inpopulated urban environments such as the downtowns of largemunicipalities (e.g., New York City, San Francisco, etc.). Moreover,parking is often in demand near destinations or event venues such asneighborhoods surrounding sports stadiums, concert halls, amusementparks, or beachfronts.

Additionally, the high price of real estate has motivated many propertyowners to seek out non-traditional ways for property owners to monetizetheir real property assets. For example, homeowners can often rent outrooms in their homes to tourists or travelers using an online homerental platform.

Therefore, a solution is needed for a parking management system toconveniently, securely and effectively allow property owners to rent outtheir available parking space(s) and for drivers seeking parking toreserve such parking spaces. In addition, such a solution should assistthe property owner in determining an appropriate rental price for theirparking spaces. Also, such a solution should be able to assist theproperty owner in maximizing their earning potential from such assets byensuring adequate turnover in parked vehicles and that empty parkingspaces are occupied quickly and efficiently. Moreover, such a solutionshould also ensure that drivers vacate rented parking spaces in time soas not to inconvenience property owners who require such spaces andsuggest appropriate penalty measures when drivers overstay theirallotted parking times.

SUMMARY

A parking management system and methods of operation are disclosed. Acomputer-implemented method of managing parking reservations over acommunications network can include receiving, in one or more databasesstored in one or more memory units, positional data concerning a listinglocation. The method can also include establishing, using one or moreprocessors of a computing system, a radius boundary based on thepositional data stored in the one or more databases and filtering, usingthe one or more processors, the one or more databases using the radiusboundary to determine an amount of parking spaces listed and the amountof parking spaces reserved within a preset time period. The method canalso include calculating, using the one or more processors, atransaction rate using the amount of parking spaces listed, the amountof parking spaces reserved, and the preset time period and storing thetransaction rate in the one or more databases. The method can alsoinclude determining, using the one or more processors, a recommendedlisting price based on the transaction rate and transmitting, over thecommunications network using one or more communication interfaces, therecommended listing price to a listing client device.

The method can also include receiving, over the communications network,one or more listing requests from one or more parking sensors. Themethod can also include receiving, over the communications network, oneor more reservation requests from at least one of one or more bookingclient devices and one or more control units of a self-driving vehicleand updating, using the one or more processors, the amount of parkingspaces listed and the amount of parking spaces reserved in the one ormore databases using the one or more listing requests and the one ormore reservation requests.

The one or more parking sensors can include a proximity detector, one ormore sensor processors, a sensor communication interface, and a portablepower supply. The one or more parking sensors can also include apositioning unit of a booking client device or the control unit of aself-driving vehicle.

The method can also include adding, using the one or more processors, abuffer period to a reservation period in response to receiving thereservation request from at least one of the booking client device andthe control unit of the self-driving vehicle. The method can alsoinclude calculating, using the one or more processors, an averagelisting price based on listing prices stored in the one or moredatabases prior to determining the recommended listing price anddetermining, using the one or more processors, the recommended listprice by calculating a listing multiplier using the transaction ratestored in the one or more databases and multiplying the listingmultiplier by the average listing price.

The method can also include calculating the listing multiplier byapplying, using the one or more processors, a logarithmic function tothe transaction rate stored in the one or more databases when thetransaction rate exceeds a rate threshold. The method can also includereceiving timestamp data from one or more sensors in a vicinity of thelisting location and storing the timestamp data in the one or moredatabases. The method can also include determining, using the one ormore processors, an average park time using the timestamp data; andtransmitting, over the communications network using the one or morecommunication interfaces, a recommended availability time calculatedusing the average park time to the listing client device. The one ormore sensors can include a positioning unit of at least one of one ormore booking client devices and one or more control units of aself-driving vehicle.

The method can also include receiving, over the communications network,a status update from a booking client device concerning an upcomingdeparture of a vehicle occupying a reserved parking space. The methodcan also include determining a real-time position of the booking clientdevice in response to receiving the status update and querying a parkingsensor in a vicinity of the reserved parking space in response to thestatus update received from the booking client device to confirm anoccupancy status of the reserved parking space.

The method can also include calculating a penalty multiplier using thetransaction rate based on the occupancy status of the reserved parking,calculating a penalty rate using the penalty multiplier and a listingprice, and transmitting, over the communications network, the penaltyrate to at least one of the booking client device and the listing clientdevice.

A computing system to manage parking reservations over a communicationsnetwork can include one or more communication interfaces, one or morememory units, one or more processors executing computer-readableinstructions stored in the one or more memory units to receive, in oneor more databases stored in the one or more memory units, positionaldata concerning a listing location, establish a radius boundary based onthe positional data stored in the one or more databases, and filter theone or more databases using the radius boundary to determine an amountof parking spaces listed and the amount of parking spaces reservedwithin a preset time period.

The computing system can also calculate a transaction rate using theamount of parking spaces listed, the amount of parking spaces reserved,and the preset time period and storing the transaction rate in the oneor more databases, determine a recommended listing price based on thetransaction rate, and transmit, over the communications network usingthe one or more communication interfaces, the recommended listing priceto a listing client device.

A non-transitory computer readable medium can include computerexecutable instructions stored thereon executed by one or moreprocessors, where the instructions include the steps of receiving, inone or more databases stored in one or more memory units, positionaldata concerning a listing location, establishing, using the one or moreprocessors of a computing system, a radius boundary based on thepositional data stored in the one or more databases, and filtering,using the one or more processors, the one or more databases using theradius boundary to determine an amount of parking spaces listed and theamount of parking spaces reserved within a preset time period. Theinstructions can also include the steps of calculating, using the one ormore processors, a transaction rate using the amount of parking spaceslisted, the amount of parking spaces reserved, and the preset timeperiod and storing the transaction rate in the one or more databases,determining, using the one or more processors, a recommended listingprice based on the transaction rate, and transmitting, over thecommunications network using one or more communication interfaces, therecommended listing price to a listing client device.

The methods, devices, or systems disclosed herein may be implemented ina variety of different ways. Certain variations have other steps orelements in addition to or in place of those mentioned above. The stepsor elements will become apparent to those skilled in the art from theaccompanying drawings or from the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a parking management system.

FIG. 2A illustrates a variation of a server of the parking managementsystem.

FIG. 2B illustrates a variation of a client device of the parkingmanagement system.

FIG. 2C illustrates a variation of a parking sensor of the parkingmanagement system.

FIG. 3A illustrates a new listing graphical user interface (GUI)displayed on a listing client device connected to the parking managementsystem.

FIG. 3B illustrates a listing information GUI displayed on a listingclient device connected to the parking management system.

FIG. 4A illustrates a reservation request GUI displayed on a bookingclient device connected to the parking management system.

FIG. 4B illustrates a reservation status GUI displayed on a bookingclient device connected to the parking management system.

FIG. 5 illustrates a schematic of a booking vehicle detected by aparking sensor at a listing location.

FIG. 6A illustrates a variation of a listing database table stored inone or more databases of the parking management system.

FIG. 6B illustrates a variation of a reservation database table storedin one or more databases of the parking management system.

FIG. 7 illustrates examples of computer readable instructions andapplication logic undertaken by the parking management system.

FIG. 8 illustrates a variation of a map overview GUI displayed on adisplay component connected to the parking management system.

FIG. 9 illustrates a method of operation of the parking managementsystem.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates that a parking management system 100 can include oneor more listing client devices 102, booking client devices 104, parkingsensors 106, or a combination thereof communicatively coupled to one ormore databases 108, application servers 110, web servers 112, serverload balancers 114, cloud load balancers 116, or a combination thereofover a communications network 118.

The communications network 118 can be any multi-hop network that coversregions, countries, continents, or a combination thereof. Examples ofthe communications network 118 can include a cellular network such as a3G network, a 4G network, a long-term evolution (LTE) network; a soniccommunication network; a satellite network; a wide area network such asthe Internet, or a combination thereof. The web servers 112, theapplication servers 110, the server load balancers 114, the cloud loadbalancers 116, or a combination thereof can be communicatively coupledto the communications network 118 through connections 120. Theconnections 120 can be wired connections, wireless connections, or acombination thereof.

The parking management system 100, or a portion therein, can include aweb and/or mobile application hosted by a computing cloud 122 such as aWindows Azure™ cloud, an Amazon Elastic Computer Cloud (Amazon EC2)™, aGoogle App Engine™, or a combination thereof. For example, the parkingmanagement system 100 can include a web and/or mobile application run onvirtual machines hosted on the one or more application servers 110, webservers 112, or a combination thereof. In one variation, the computingcloud 122 can include the one or more application servers 110, webservers 112, databases 108, server load balancers 114, cloud loadbalancers, portions therein, or a combination thereof. The parkingmanagement system 100 can rely on processing and storage resourcesprovided by the one or more application servers 110, web servers 112,databases 108, server load balancers 114, cloud load balancers 116, or acombination thereof.

The cloud load balancers 116 can provide traffic load balancing anddistribute client requests among multiple web servers 112. The webservers 112 can include HTTP servers or rely on the computing cloud 122to handle HTTP requests. The web servers 112 can also be instantiatedand managed by the computing cloud 122.

The server load balancer 114 can balance interactions between the webservers 112 and the one or more application servers 110. The applicationservers 110 can handle application logic and interacts with thedatabases 108 to store data and application states. The web servers 112,the application servers 110, or a combination thereof can include rackmount servers, cluster servers, blade servers, main frames, dedicateddesktops or laptops, or a combination thereof

The databases 108 can be one or more SQL databases. The applicationservers 110 can interface with one or more SQL servers managing the SQLdatabases. The application data and application states can be stored ina cloud managed SQL database. In other variations, the database 108 canbe a document-oriented database including a NoSQL database such as aMongoDB® database.

The application servers 110, the web servers 112, the cloud loadbalancers 116, the server load balancers 114, and the cloud SQLdatabases 108 can be any of the servers, load balancers, and databasesdiscussed in U.S. Pat. No. 9,176,773, the content of which is herebyincorporated by reference in its entirety.

The listing client devices 102, the booking client devices 104, or acombination thereof can include a portable computing device such as asmartphone, a tablet, a laptop, a smartwatch, a personal entertainmentdevice, or a combination thereof. In other variations, the listingclient device 102, the booking client device 104, or a combinationthereof can include a desktop computer. The listing client device 102can be used by a user of the parking management system 100 to list aparking space for rental or lease by other users of the parkingmanagement system 100. The booking client device 104 can be used by auser of the parking management system 100 to book a parking space listedfor rental or lease on the parking management system 100.

The parking management system 100 can also include one or more parkingsensors 106. The parking sensors 106 can be located at a listinglocation 124. In one variation, the parking sensor 106 can include thesensing components shown in FIG. 2C. In other variations, the parkingsensor 106 can refer to a client device such as the listing clientdevice 102, the booking client device 104, or parts therein.

The parking management system 100 can be communicatively coupled to acontrol unit 126 of a self-driving vehicle 128. For example, the parkingmanagement system 100 can receive data or client requests from thecontrol unit 126 of the self-driving vehicle 128. The self-drivingvehicle 128 can include motor vehicles or vessels having an autonomousor semiautonomous driving mode. For example, the self-driving vehicle128 can be vehicles disclosed or discussed in U.S. Pat. No. 9,120,485,U.S. Pat. No. 8,965,621, and U.S. Pat. No. 8,954,217, the contents ofwhich are hereby incorporated by reference in their entireties.

FIG. 2A illustrates that a server 200 of the parking management system100 can have one or more processors 202, a memory 204, and acommunication interface 206. The processors 202 can be coupled to thememory 204 and the communication interface 206 through high-speed buses208. The server 200 can represent any of the web servers 112, theapplication servers 110, or a combination thereof of FIG. 1 .

The processors 202 can include one or more central processing units(CPUs), graphical processing units (GPUs), Application-SpecificIntegrated Circuits (ASICs), field-programmable gate arrays (FPGAs), ora combination thereof. The processors 202 can execute software orcomputer-readable instructions stored in the memory 204 to execute themethods or operations described herein. The processors 202 can beimplemented in a number of different manners. For example, theprocessors 202 can include one or more embedded processors, processorcores, microprocessors, logic circuits, hardware finite state machines(FSMs), digital signal processors (DSPs), or a combination thereof. Forexample, the processors 202 can be 64-bit processors.

The memory 204 can store software, data, logs, or a combination thereof.The memory 204 can be an internal memory. Alternatively, the memory 204can be an external memory, such as a memory residing on a storage node,a cloud server, or a storage server. The memory 204 can be a volatilememory or a non-volatile memory. For example, the memory 204 can be anonvolatile storage such as non-volatile random access memory (NVRAM),Flash memory, disk storage, or a volatile storage such as static randomaccess memory (SRAM). The memory 204 can be the main storage unit forthe server 200.

The communication interface 206 can include one or more wired orwireless communication interfaces. For example, the communicationinterface 206 can be a network interface card of the server 200. Thecommunication interface 206 can be a wireless modem or a wired modem. Inone variation, the communication interface 206 can be a Wi-Fi modem. Inother variations, the communication interface 206 can be a 3G modem, a4G modem, an LTE modem, a Bluetooth® component, a radio receiver, anantenna, or a combination thereof. The server 200 can connect to orcommunicatively couple with the communications network 118 using thecommunication interface 206. The server 200 can transmit or receivepackets or messages using the communication interface 206.

FIG. 2B illustrates that a client device 210 of the parking managementsystem 100 can have a client processor 212, a client memory 214, aclient communication unit 216, a locational unit 218 having a globalpositioning system (GPS) receiver, and a display 220. The clientprocessor 212 can be coupled to the client memory 214, the clientcommunication unit 216, and the locational unit 218 through high-speedbuses 222.

The client processor 212 can include one or more CPUs, GPUs, ASICs,FPGAs, or a combination thereof. The client processor 212 can executesoftware stored in the client memory 214 to execute the methodsdescribed herein. The client processor 212 can be implemented in anumber of different manners. For example, the client processor 212 canbe an embedded processor, a processor core, a microprocessor, a logiccircuit, a hardware FSM, a DSP, or a combination thereof. As a morespecific example the client processor 212 can be a 32-bit processor suchas an ARM® processor.

The client memory 214 can store software, data, logs, or a combinationthereof. In one variation, the client memory 214 can be an internalmemory. In another variation, the client memory 214 can be an externalstorage unit. The client memory 214 can be a volatile memory or anon-volatile memory. For example, the client memory 214 can be anonvolatile storage such as NVRAM, Flash memory, disk storage, or avolatile storage such as SRAM. The client memory 214 can be the mainstorage unit for the client device 210.

The client communication unit 216 can be a wired or wirelesscommunication interface. For example, the client communication unit 216can be a network interface card of the client device 210. The clientcommunication unit 216 can be a wireless modem or a wired modem. In onevariation, the client communication unit 216 can be a Wi-Fi modem. Inother variations, the client communication unit 216 can be a 3G modem, a4G modem, an LTE modem, a Bluetooth® component, a radio receiver, anantenna, or a combination thereof. The client device 210 can connect toor communicatively couple with the communications network 118 using theclient communication unit 216. The client device 210 can transmit orreceive packets or messages using the client communication unit 216.

The locational unit 218 can include a GPS component such as the GPSreceiver, an inertial unit, a magnetometer, a compass, or a combinationthereof. The locational unit 218 can receive GPS signals from a GPSsatellite. The inertial unit can be implemented as a multi-axisaccelerometer including a three-axis accelerometer, a multi-axisgyroscope including a three-axis MEMS gyroscope, or a combinationthereof.

The display 220 can be a touchscreen display such as a liquid crystaldisplay (LCD), a thin film transistor (TFT) display, an organiclight-emitting diode (OLED) display, or an active-matrix organiclight-emitting diode (AMOLED) display. In certain variations, thedisplay 220 can be a retina display, a haptic touchscreen, or acombination thereof. For example, when the client device 210 is asmartphone, the display 220 can be the touchscreen display of thesmartphone.

The client device 210 can refer to any of the listing client device 102,the booking client device 104, or a combination thereof. For purposes ofthe present disclosure, the client processor 212 can refer to aprocessor of the listing client device 102, the booking client device104, or a combination thereof. Moreover, the client memory 214 can referto a memory of the listing client device 102, the booking client device104, or a combination thereof. In addition, the client communicationunit 216 can refer to a communication unit of the listing client device102, the booking client device 104, or a combination thereof.Furthermore, the locational unit 218 can refer to a locational unit orGPS receiver of the listing client device 102, the booking client device104, or a combination thereof. Additionally, the display 220 can referto the display of the listing client device 102, the booking clientdevice 104, or a combination thereof.

For example, the servers 200 and client devices 210 disclosed herein caninclude the type of computing systems and mobile computing devicesdisclosed or discussed in U.S. Pat. No. 9,305,310, the content of whichis hereby incorporated by reference in its entirety.

FIG. 2C illustrates that the parking sensor 106 can include a sensorprocessor 224, a sensor memory 226, a sensor communication interface228, a proximity detector 230, a portable power supply 232, or acombination thereof. In other variations, the parking sensor 106 caninclude a sensor locational unit 234 having a global positioning system(GPS) receiver, a camera unit 236, or a combination thereof. The sensorprocessor 224 can be coupled to the sensor memory 214, the sensorcommunication interface 228, the proximity detector 230, the portablepower supply 232, or a combination thereof through high-speed buses 222.

The sensor processor 224 can include one or more CPUs, GPUs, ASICs,FPGAs, or a combination thereof. The sensor processor 224 can executesoftware stored in the sensor memory 226 to execute the methods oroperations described herein. The sensor processor 224 can be implementedin a number of different manners. For example, the sensor processor 224can include a processor core, a microprocessor, a logic circuit, a DSP,or a combination thereof. As a more specific example the sensorprocessor 224 can include a 16-bit or 32-bit processor such as an ARM™processor.

The sensor memory 226 can store software, data, logs, or a combinationthereof. In one variation, the sensor memory 226 can be an internalmemory. In another variation, the sensor memory 226 can be an externalstorage unit. The sensor memory 226 can be a volatile memory or anon-volatile memory. For example, the sensor memory 226 can be anonvolatile storage such as NVRAM, Flash memory, disk storage, or avolatile storage such as SRAM.

The sensor communication interface 228 can be a wired or wirelesscommunication interface. For example, the sensor communication interface228 can be a network interface card of the parking sensor 106. Thesensor communication interface 228 can be a wireless modem or a wiredmodem. In one variation, the sensor communication interface 228 can be aWi-Fi modem. In other variations, the sensor communication interface 228can be a 3G modem, a 4G modem, an LTE modem, a Bluetooth® component, aradio receiver, an antenna, or a combination thereof. The parking sensor106 can connect to or communicatively couple with the communicationsnetwork 118 using the sensor communication interface 228. The parkingsensor 106 can transmit or receive information or messages in the formof data packets using the sensor communication interface 228.

The proximity detector 230 can include an infrared (IR) lighttransceiver, an IR distance sensor, an ultrasonic transmitter anddetector, or a combination thereof. The parking sensor 106 can use theproximity detector 230 to detect the presence of a vehicle in a certainvicinity of the parking sensor 106. For example, the parking sensor 106can detect that a vehicle is near the parking sensor 106 when a portionof the vehicle, such as the chassis of the vehicle, covers or obscuresthe proximity detector 230 or a portion therein. In another variation,the parking sensor 106 can detect the presence of a vehicle when a partof the vehicle affects or interferes with a behavior of light oracoustic waves emitted, reflected, or received by the parking sensor106.

The sensor locational unit 234 can include a GPS component such as a GPSreceiver, an inertial unit, a magnetometer, a compass, or a combinationthereof. The sensor locational unit 234 can receive GPS signals from aGPS satellite. The inertial unit can be implemented as a multi-axisaccelerometer including a three-axis accelerometer, a multi-axisgyroscope including a three-axis MEMS gyroscope, or a combinationthereof. The parking sensor 106 can also include a camera unit 236. Thecamera unit 236 can capture static images, video images, or acombination thereof and store the images in the sensor memory 226.

The sensor processor 224 can be coupled to the sensor memory 226, thesensor communication interface 228, the sensor locational unit 234, theproximity detector 230, and the camera unit 236 through high-speed buses238.

FIG. 3A illustrates that a listing user of the parking management system100 can list a parking space for rent or lease by applying a user inputto a new listing graphical user interface (GUI) 300 displayed on alisting client device 102. The listing user can list the parking spaceby applying a user input to a button or link displayed as part of thenew listing GUI 300. The listing user can transmit a listing request 304to the application servers 110 in response to applying the user input tothe button or link.

The listing request 304 can be transmitted as one or more communicationpackets, such as transmission control protocol (TCP) packets, containinga header and a payload. The listing request 304 can be received by theweb servers 112, the application servers 110, or a combination thereofand stored in the database 108.

The new listing GUI 300 can be rendered through an application 302. Inone variation, the application 302 can be written using the Xcode™programming language, the Swift™ programming language, or a combinationthereof. In other variations, the application 302 can be written usingthe Java™ programming language, the Objective-C programming language, ora C programming language.

FIG. 3B illustrates that the listing user can input informationconcerning the parking space through a listing information GUI 306. Thelisting user can enter a type 308 of parking space, a listing location310, a listing price 312, an availability window 314, or a combinationthereof. The type 308 of parking space can include a driveway space, aparking space in a residential or commercial garage, a parking space ina parking lot, a front yard or back yard space, a curb space, a meteredspace, or a combination thereof.

The listing location 310 can include an address of a residence,building, or other location providing the parking space. The listinguser can manually enter a geographic address for the listing location310 through the listing information GUI 306. In this case, theapplication server 110 can transmit the geographic address to a mapdatabase, such as a Geographic Information System (GIS) database or aGoogle Maps® database and query the map database for positionalcoordinates corresponding to the geographic address. The applicationserver 110 can then store the positional coordinates in the database108. In another variation, the user can use the locational unit 218 ofthe listing client device 102 to provide positional coordinates for thelisting location 310 when the user is at the listing location 310.

The listing price 312 can include an hourly rate or price requested bythe user for the parking space. The availability window 314 can be atime window when the parking space is available for rent or lease. Forexample, the availability window 314 can range from 30 minutes to 30days. The listing request 304 can include data concerning the type 308of parking space, the listing location 310, the listing price 312, theavailability window 314, or a combination thereof.

In other variations, the listing request 304 can be transmitted directlyfrom the parking sensor 106. The parking sensor 106 can automaticallytransmit the listing request 304 to the application servers 110 when theparking sensor 106 detects a vehicle has departed a parking space in thevicinity of the parking sensor 106. For example, the parking sensor 106can be configured to store information concerning the listing location310, the listing price 312, the availability window 314, and the type308 of listing in the sensor memory 226. The parking sensor 106 canautomatically transmit a listing request 304 containing such data orinformation as soon as the space is vacant. As a more specific example,the parking sensor 106 can be a sensor embedded in a driveway of aresidence and the parking sensor 106 can transmit the listing request304 as soon as a vehicle previously occupying the driveway vacates thedriveway.

FIG. 4A illustrates that a booking user of the parking management system100 can reserve a parking space listed by a listing user through areservation request GUI 400. The booking user can reserve a parkingspace in a desired booking location 402 by manually entering ageographic address. In addition, the booking user can apply an input toa current location icon 404 displayed on the reservation request GUI 400to prompt the locational unit 218 of the booking client device 104 totransmit the current geographic coordinates of the booking client device104 to the application servers 110 , the cloud-managed database 108, ora combination thereof. Moreover, the booking user can draw a radiusboundary around a portion of a map graphic 408 displayed on thereservation request GUI 400.

The reservation request GUI 400 can display parking space listings 406in list form or overlaid on the map graphic 408. Each space listings 406can include information concerning the listing location 310, the listingprice 312, or the availability window 314 associated with the spacelisting 406. Once the booking user has found a desired parking space,the booking user can select the space listing 406 to place a reservationrequest 410. For example, the booking user can apply a user input to anicon associated with the space listing 406 and then press a reservationbutton to place the reservation request 410.

FIG. 4B illustrates that the booking user can view a current status of areserved parking space 414 once a reservation has been placed using theparking management system 100. The booking user can view the currentstatus of the reservation through a reservation status GUI 412. Thereservation status GUI 412 can include a timer 416 counting down areservation period 418. In other variations, the reservation status GUI412 can display an accrued cost of the reservation. The booking user canapply a user input to a departure button to transmit a status update 420to the parking management system 100 that a booking vehicle 422 iseither in the process of departing the reserved parking space 414 or hasdeparted the reserved parking space 414.

In another variation, the booking client device 104 can receive one ormore messages or notifications from the parking management system 100concerning the expiration of the reservation period 418. For example,the messages can include a text messages, such as a Short MessageService (SMS) message, a Multimedia Messaging Service (MMS) message, ora combination thereof. The messages can include a link to prompt thebooking client device 104 to open the application 302 and display thereservation status GUI 412. The link can be a deep linking uniformresource locator (URL) address directing the booking client device 104to open a specific page of the application 302.

In other variations, the booking vehicle 422 can be a self-drivingvehicle 128 and the control unit 126 of the self-driving vehicle 128 canautomatically transmit the reservation request 410 without input fromthe booking user. The reservation request 410 can include presetinformation or data concerning the parking space desired by an occupantor owner of the self-driving vehicle 128 including a listing location310, the listing price 312, the type 308 of listing, or a combinationthereof. The parking management system 100 can receive the reservationrequest 410 directly from the control unit 126 of the self-drivingvehicle 128 and parse the reservation request 410 for data orinformation concerning the listing location 310, the listing price 312,the type 308 of listing, or a combination thereof. The parkingmanagement system 100 can then filter the one or more databases 108 toselect a listing 406 matching the criteria included in the reservationrequest 410.

The parking management system 100 can also receive the status update 420directly from the control unit 126 of the self-driving vehicle 128without input from the booking user. The status update 420 can indicatethat the self-driving vehicle 128 is departing or has departed thereserved parking space 414.

The listing client device 102, the booking client device 104, theparking sensors 106, or a combination thereof can encrypt requests,including a listing request 304 or a reservation request 410, beforetransmitting the request. The listing client device 102, the bookingclient device 104, the parking sensors 106, or a combination thereof canencrypt the requests using an encryption protocol such as a secure hashalgorithm (SHA). The encryption protocol can be a SHA-256 hash function,a SHA-384 hash function, or any type of SHA-2 certificate or function.The listing client device 102, the booking client device 104, theparking sensors 106, or a combination thereof can securely transmit theencrypted request over the communications network 118 to servers orother devices in the computing cloud 122.

FIG. 5 illustrates that the parking management system 100 can query aparking sensor 106 in a vicinity of the reserved parking space 414 inresponse to the status update 420 received from the booking clientdevice 104 to confirm an occupancy status of the booking vehicle 422.For example, the application server 110 can ping the parking sensor 106and request the last proximity measurement from the sensor memory 226.The application server 100 can also ping the parking sensor 106 toactivate the proximity detector 230 of the parking sensor 106 and querythe parking sensor 106 for a real-time proximity measurement.

In another variation, the parking management system 100 can activate thecamera unit 236 of the parking sensor 106 and instruct the camera unit236 to capture images of the environment surrounding the reservedparking space 414. The parking sensor 106 can then transmit the imagesto the one or more application servers 110 for analysis by an imagerecognition protocol executed by the one or more processors 202.

In variations where the parking sensor 106 refers to a listing clientdevice 102 or portions therein, the application servers 110 can transmitone or more messages to the listing client device 102 to confirm thatthe booking vehicle 422 has departed the reserved parking space 414.

FIG. 6A illustrates that the database 108 can store in one or moredatabase tables 600 positional data 602 concerning a listing location310. The one or more databases 108 can include a cloud managed SQLdatabase such as Microsoft Azure® database. The one or more databases108 can be stored in a memory 204 of the computing cloud 122.

One or more servers responsible for managing the database 108 canreceive the positional data 602 from a map database, such as a GoogleMaps® database, after querying the map database with a geographicaddress received from the booking client device 104. In othervariations, the web servers 112, the application servers 110, or acombination thereof can receive the positional data 602 directly fromthe locational unit 218 of the booking client device 104.

The positional data 602 can include latitudinal and longitudinalcoordinates. For example, the positional data 602 can include latitudeand longitude coordinates in the Universal Traverse Mercator (UTM)coordinate system.

The database 108 can store the positional data 602 concerning thelisting location 310 in one or more listing database tables 604. Theapplication servers 110 can also parse the listing request 304 receivedfrom the booking client device 104, the control unit 126 of theself-driving vehicle 128, or a combination thereof and store data orinformation concerning the type 308 of parking space, the listing price312, the availability window 314, or a combination thereof in thelisting database tables 604.

FIG. 6B illustrates that the database 108 can also include one or morereservation database tables 606. The reservation database tables 606 caninclude data or information obtained from the reservation request 410including the type 308 of parking space, the reservation period 418,positional data 602 concerning the reserved parking space 414, or acombination thereof. The reservation database tables 606 can alsoinclude data or information concerning an occupancy status 608 of thereserved parking space 414, a buffer period 610, and/or an actualparking time 614 based on timestamps 612 received from the listingclient device 102 or the parking sensors 106.

The parking management system 100 can determine the occupancy status 608of a reserved parking space 414 by querying or pinging one or moreparking sensors 106 in a vicinity of the reserved parking space 414. Inanother variation, the parking management system 100 can determine theoccupancy status 608 of a reserved parking space 414 by receiving aconfirmation signal or message from a listing client device 102. Forexample, the parking management system 100 can transmit a text messageto the listing client device 102 containing a link directing the listinguser to confirm that a booking vehicle 422 has vacated the reservedparking space 414.

The parking management system 100 can also add a buffer period 610 tothe reservation period 418 of a reservation request 410 stored in thereservation database tables 606. The parking management system 100 canset the buffer period 610 based on the length of the reservation period418. For example, the parking management system 100 can set the bufferperiod 610 as half the length of the reservation period 418 initiallyrequested by a booking user. In another variation, the parkingmanagement system 100 can automatically set a buffer period 610 of onehour for all reservations exceeding 30 minutes.

The parking management system 100 can permit the booking user to extendthe reservation period 418 up to the end of the buffer period 610. Forexample, when a booking user initially requests a reservation period 418of one hour, the parking management system 100 can automatically set thebuffer period 610 for this reservation as 30 minutes. In this case, theparking management system 100 can allow the booking user to park theuser's vehicle in the reserved parking space 414 for up to 1.5 hours.The parking management system 100 can charge the booking user anadditional fee for the extension. Upon reaching the end of the bufferperiod 610, the parking management system 100 can prevent the bookinguser from extending the reservation period 418 any longer and requirethe booking user to initiate a new reservation request 410.

When a buffer period 610 is added to a reservation period 418, theparking management system 100 can ensure the listing 406 does not appearas an entry in any database tables listing available or unoccupiedparking spaces during the pendency of the reservation period 418 and thebuffer period 610. The parking management system 100 can add a bufferperiod 610 to all reservation requests 410 received from booking clientdevices 104 and/or the control units 126 of all self-driving vehicles128.

The databases 108 can also store timestamps 612 received from listingclient devices 102, booking client devices 104, parking sensors 106, ora combination thereof. The listing client devices 102, the parkingsensors 106, or a combination thereof can transmit timestamps 612 inconnection with the transmission of listing requests 304. The bookingclient devices 104 can transmit timestamps 612 in connection with thetransmission of reservation requests 410. The parking sensors 106, thelisting client devices 102, or a combination thereof can also transmittimestamps 612 in connection with the transmission of status updates 420or when the occupancy status 608 of a reserved parking space 414changes.

The reservation database table 606 can also store actual parking times614 based on the timestamps 612 received. The parking management system100 can determine the actual parking times 614 based on timestamps 612received when a booking vehicle 422 occupies the reserved parking space414 and the same booking vehicle 422 vacates the reserved parking space414. The actual parking times 614 can differ from the reservationperiods 418 included in the reservation requests 410.

The database tables 600 can also keep track of a listing count 616 and areservation count 618. The listing count 616 can correspond to thenumber or amount of parking spaces listed using the parking managementsystem 100 during a given time period. The reservation count 618 cancorrespond to the number or amount of parking spaces reserved using theparking management system 100 during a given time period. For example,the listing count 616 can correspond to the number of listing requests304 received by the parking management system 100 within a given timeperiod. The reservation count 618 can correspond to the number ofreservation requests 410 received by the parking management system 100within a given time period. The parking management system 100 cancontinuously update the one or more database tables 600, including thelisting count 616 and the reservation count 618, based on the number oflisting requests 304 and the number of reservation requests 410received.

FIG. 7 illustrates that one or more processors 202 of the parkingmanagement system 100 can execute computer-readable instructions storedin a memory 204 of the computing cloud 122 in order to determine arecommended list price 700. The parking management system 100 candetermine the recommended list price 700 in response to a listingrequest 304 received from a listing client device 102.

The parking management system 100 can determine the recommended listprice 700 by first establishing a radius boundary 702 based on thepositional data 602 received from the listing client device 102. Theparking management system 100 can retrieve the positional data 602stored in the one or more databases 108 and establish the radiusboundary 702 using the coordinates of the position data 602 as thecenter point. For example, the parking management system 100 canestablish the radius boundary 702 as the boundary or demarcation of aone mile or one kilometer radius. The parking management system 100 canset the size of the radius boundary 702 based on a geographic criterionsuch as a size of the municipality or geographic region in which thepositional data 602 is located. The parking management system 100 canalso adjust the radius boundary 702 based on a time-of-day, aday-of-the-week, a month, a season, or a combination thereof

The parking management system 100 can then filter the one or moredatabases 108 using the radius boundary 702 and a preset time period704. The preset time period 704 can range from 10 minutes to 10 days. Inother variations, the preset time period 704 can be more than 10 days.The preset time period 704 can be adjusted by an administrator of theparking management system 100. The parking management system 100 canfilter the one or more listing database tables 604 using the radiusboundary 702 and the positional data 602 of all other listing requests304 received within the preset time period 704 to determine the listingcount 616. The parking management system 100 can also filter the one ormore reservation database tables 606 using the radius boundary 702 andthe positional data 602 of all reservation requests 410 received withinthe preset time period 704 to determine the reservation count 618.

The parking management system 100 can then calculate a transaction rate706 using the listing count 616 and the reservation count 618. Thetransaction rate 706 can be calculated by summing the listing count 616and the reservation count 618. The transaction rate 706 can becalculated by summing the listing count 616 and the reservation count618 to yield a total count and then dividing the total count by thepreset time period 704. The transaction rate 706 can also be equivalentto either the reservation count 618 or the listing count 616. Theparking management system 100 can store the transaction rate 706 in oneor more database tables 600 and update the transaction rate 706 as newlisting requests 304 are received.

The transaction rate 706 can also be calculated by taking a ratio of thereservation count 618 and the listing count 616 and or by dividing thereservation count 618 by the listing count 616. The parking managementsystem 100 can also calculate the transaction rate 706 by adding theratio of the reservation count 618 and the listing count 616 to any ofthe listing count 616, the reservation count 618, or a sum thereof.

The parking management system 100 can then calculate a listingmultiplier 708 using the transaction rate 706. The parking managementsystem 100 can calculate the listing multiplier 708 by applying a firstlogarithmic function 710 to the transaction rate 706 when thetransaction rate 706 exceeds a first rate threshold 712. For example,the first rate threshold 712 can be a rate of 10 listings and/orrequests per minute and the parking management system 100 can apply alog 10 function to the transaction rate 706 when the transaction rate706 exceeds the first rate threshold 712. When the transaction rate 706does not exceed the first rate threshold 712, the parking managementsystem 100 can apply a second logarithmic function 714 to thetransaction rate 706 when the transaction rate 706 exceeds a second ratethreshold 716. The first rate threshold 712 can be different from thesecond rate threshold 716. For example, the first rate threshold 712 canbe greater than the second rate threshold 716. The second logarithmicfunction 714 can be a natural log function.

The parking management system 100 can determine the recommended listingprice 700 by multiplying the listing multiplier 708 by an averagelisting price 718. The parking management system 100 can calculate theaverage listing price 718 by taking an average of the listing prices 312stored in the filtered instance of the listing database tables 604.After calculating the recommended listing price 700, the applicationservers 110 can transmit the recommended listing price 700 to thelisting client device 102 over the communications network 118.

The parking management system 100 can also determine an average parktime 720 based on the actual parking times 614 stored in the filteredinstance of the reservation database table 606. The parking managementsystem 100 can then transmit a recommended availability time 724 to thelisting client device 102 equivalent to the average park time 720. Inother variations, the parking management system 100 can multiply theaverage park time 720 by a multiplier to yield the recommendedavailability time 724.

The parking management system 100 can also ensure a booking user doesnot abuse the system by occupying a reserved parking space 414 past theend of the reservation period 418. The parking management system 100 canreceive, over the communications network 118, a status update 420concerning a departure or upcoming departure of a booking vehicle 422from a reserved parking space 414.

The parking management system 100 can determine a real-time position ofthe booking client device 104 associated with the booking vehicle 422 inresponse to receiving the status update 420. The parking managementsystem 100 can determine a real-time position 724 of the booking clientdevice 104 by querying a map database such as a Google Maps® database.In another variation, the parking management system 100 can determine areal-time position 724 of the booking client device 104 by directlytracking a locational unit 218 of the booking client device 104.

When the real-time position 724 of the booking client device 104 is notin a vicinity of the listing location 310 of the reserved parking space414, such as when the booking client device 104 is outside the radiusboundary 702, the parking management system 100 can query the parkingsensor 106 in the vicinity of the reserved parking space 414 to confirmthe occupancy status 608 of the reserved parking space 414. In anothervariation, the parking management system 100 can query the listingclient device 102 to confirm the occupancy status 608 of the reservedparking space 414 by requesting the listing user enter a user input toconfirm the departure of the booking vehicle 422. In other variations,when the booking vehicle 422 is a self-driving vehicle 128, the parkingmanagement system 100 can ping the control unit 126 of the self-drivingvehicle 128 for a real-time position of the self-driving vehicle 128.

The parking management system 100 can calculate a penalty rate 726 usinga penalty multiplier 728. In one variation, the penalty multiplier 728can be equivalent to the listing multiplier 708. In other variations,the penalty multiplier 728 can be greater than the listing multiplier708, such as double the value of the listing multiplier 708. The parkingmanagement system 100 can calculate the penalty rate 726 by multiplyingthe listing price 312 by the penalty multiplier 728. The parkingmanagement system 100 can transmit, over the communications network 118,the penalty rate 726 to the booking client device 104, the listingclient device 102, or a combination thereof.

FIG. 8 illustrates that the parking management system 100 can determinea causal point-of-interest (POI) 800 using the transaction rate 706 andpositional data 602 included in the listing requests 304 and reservationrequests 410 received by the parking management system 100 within apreset time period 704. The parking management system 100 can determinethe causal POI 800 when the transaction rate 706 within a certain radiusboundary 702 exceeds a rate threshold such as five or ten listingsand/or requests per minute. The radius boundary 702 can be establishedwhen the parking management system 100 receives the first listingrequest 304 or reservation request 410.

The causal POI 800 can be a location or venue causing a surge or suddenincrease in demand for parking within a vicinity of the causal POI 800.For example, the causal POI 800 can include a sports stadium, a concerthall, a nightclub, a movie theater, a museum, or a restaurant. Thecausal POI 800 can also include a location of an event such as a site ofa farmer's market, a political gathering, or a parade route.

The parking management system 100 can determine the causal POI 800 bycalculating a centroid of a polygon created by the positionalcoordinates of listing requests 304 or reservation requests 410 receivedwithin a preset time period 704. For example, three reservation requests410 can be received within a 60 second period and the parking managementsystem 100 can calculate the centroid of a triangle having vertices atthe three desired booking locations 402 included in the threereservation requests 410.

The parking management system 100 can also determine the causal POI 800using a request trajectory 802. The request trajectory 802 can be thetrajectory or direction of travel of a vehicle or other mode oftransportation carrying a booking client device 104. In othervariations, the request trajectory 802 can be the trajectory ordirection of travel of a self-driving vehicle 128 transmitting areservation request 410.

When the parking management system 100 determines the location of thecausal POI 800, the parking management system 100 can send one or morenotifications, messages, or alerts to user client devices in thevicinity of the causal POI 800 to alert such users to list their parkingspaces using the parking management system 100. The parking managementsystem 100 can send notifications, messages, or alerts to client devicesof users who have previously listed their parking spaces using theparking management system 100. The parking management system 100 canalso send notifications, messages, or alerts to user client devicesalong the request trajectory 802 or along a route leading to the causalPOI 800.

FIG. 9 illustrates that a computer-implemented method 900 of managingparking reservations over the communications network 118 can includereceiving, in one or more databases 108 stored in one or more memoryunits 204, positional data 602 concerning a listing location 310. Thepositional data 602 or address of the listing location 310 can betransmitted by a listing client device 102 in step 902. The positionaldata 602 or address of the listing location 310 can also be transmittedby a parking sensor 106 in step 904. When the listing client device 102or parking sensor 106 transmits an address, the application servers 110can query a map or GIS database for the positional coordinates of theaddress in step 906. The application servers 110 can interact with themap or GIS database through a map API such as the Google Maps® APL

The method 900 can also include establishing, using one or moreprocessors 202, a radius boundary 702 based on the positional data 602stored in the one or more databases 108 in step 908. The method 900 canalso include filtering, using the one or more processors 202, the one ormore databases 108 using the radius boundary 702 to determine thelisting count 616 representing an amount of parking spaces listed andthe reservation count 618 representing the amount of parking spacesreserved within a preset time period 704 in step 910.

The method 900 can also include calculating, using the one or moreprocessors 108, a transaction rate 706 using the listing count 616, thereservation count 618, and the preset time period 704 and storing thetransaction rate 706 in the one or more databases 108 in step 912. Themethod 900 can also include calculating an average listing price 718 instep 914. The method 900 can also include calculating a listingmultiplier 708 in step 916. The method 900 can include determining,using the one or more processors 108, a recommended listing price 700based on the average listing price 718 and the listing multiplier 708.The method 900 can include transmitting the recommended listing price700 to the listing client device 102 over the communications network 118in step 920.

The method 900 can also include the application servers 110 receiving astatus update 420 concerning the departure of a booking vehicle 422 froma reserved parking space 414. For example, a booking client device 104can transmit the status update 420 in step 922. The method 900 caninclude determining a real-time position 724 of the booking clientdevice 104 in response to receiving the status update 420 in step 924.The method 900 can also include querying a parking sensor 106 in thevicinity of the reserved parking space 414 in response to the statusupdate to confirm an occupancy status 608 of the reserved parking space414 in step 926. The method 900 can also include calculating a penaltyrate 726 using a penalty multiplier 728 when the system determines thebooking vehicle 422 has overstayed the end of the reservation period 418in step 928.

The system and methods described herein provides an improvement in theway parking data or information is managed and stored in a cloud manageddatabase. In addition, by calculating a recommended listing price 700based on a transaction rate 706 corresponding to the rate at whichparking listings are added and reservation requests are received, thesystem provides an improvement in the field of parking management beyondrecommending prices based on static inventory levels.

A number of variations have been described. Nevertheless, it will beunderstood by one of ordinary skill in the art that variousmodifications may be made without departing from the spirit and scope ofthe variations. In addition, the flowcharts or logic flows depicted inthe figures do not require the particular order shown, or sequentialorder, to achieve desirable results. In addition, other steps oroperations may be provided, or steps or operations may be eliminated,from the described flows, and other components may be added to, orremoved from, the described systems. Accordingly, other variations arewithin the scope of the following claims.

It will be understood by one of ordinary skill in the art that thevarious methods disclosed herein may be embodied in a non-transitoryreadable medium, machine-readable medium, and/or a machine accessiblemedium comprising instructions compatible, readable, and/or executableby a processor or processing unit of a machine, device, or computingdevice. The structures and modules in the figures may be shown asdistinct and communicating with only a few specific structures and notothers. The structures may be merged with each other, may performoverlapping functions, and may communicate with other structures notshown to be connected in the figures. Accordingly, the specificationand/or drawings may be regarded in an illustrative rather than arestrictive sense.

1. (canceled)
 2. A parking management system comprising: a memory; andone or more processors coupled to the memory, the one or more processorsbeing configured to: receive parking location data relating to a parkinglocation from a listing client device; determine a radius boundary basedon the parking location data, wherein the radius boundary is centered onthe parking location; determine a number of listings within the radiusboundary; determine a recommended listing price for the parking locationbased on the parking location data and one or more parameters includingthe number of listings within the radius boundary; and transmit a signalincluding the recommended listing price to the listing client device. 3.The parking management system of claim 2, wherein the parking locationdata received from the listing client device includes at least one of atype of the parking location, a size of the parking location, anavailability time period of the parking location, a preferred listingprice, and a distance to an event venue.
 4. The parking managementsystem of claim 2, wherein the one or more parameters include at leastone of a number of available listings, a number of occupied listings,and an average listing price of the listings within the radius boundary.5. The parking management system of claim 2, wherein determining theradius boundary is based on a size of a geographic region in which theparking location is located.
 6. The parking management system of claim2, wherein the one or more processors are configured to: adjust theradius boundary based on the number of listings within the radiusboundary.
 7. The parking management system of claim 2, wherein the oneor more processors are configured to: adjust the radius boundary basedon a time of day, a day of week or month, a season, or a combinationthereof.
 8. The parking management system of claim 2, wherein the one ormore processors are configured to: determine a recommended availabilitytime for the parking location; and transmit the signal including therecommended availability time to the listing client device.
 9. Theparking management system of claim 2, wherein the one or more processorsare configured to: determine that the number of listings within theradius boundary is below a listing threshold; and transmit an alertsignal to the listing client device to list the parking location forrent.
 10. The parking management system of claim 2, wherein the one ormore processors are configured to: determine a recommended penalty ratefor the parking location, wherein the recommended penalty rate ischarged when a use time of the parking location exceeds a reservationtime period.
 11. The parking management system of claim 2, whereindetermining the recommended listing price includes: determining atransaction rate for the listings within the radius boundary, whereinthe transaction rate is the number of the listings within the radiusboundary divided by a predetermined time period.
 12. A methodcomprising: receiving parking location data relating to a parkinglocation from a listing client device; determining a radius boundarybased on the parking location data, wherein the radius boundary iscentered on the parking location; determining a number of listingswithin the radius boundary; determining a recommended listing price forthe parking location based on the parking location data and one or moreparameters including the number of listings within the radius boundary;and transmitting a signal including the recommended listing price to thelisting client device.
 13. The method of claim 12, wherein the parkinglocation data received from the listing client device includes at leastone of a type of the parking location, a size of the parking location,an availability time period of the parking location, a preferred listingprice, and a distance to an event venue.
 14. The method of claim 12,wherein the one or more parameters include at least one of a number ofavailable listings, a number of occupied listings, and an averagelisting price of the listings within the radius boundary.
 15. The methodof claim 12, wherein determining the radius boundary is based on a sizeof a geographic region in which the parking location is located.
 16. Themethod of claim 12, further comprising: adjusting the radius boundarybased on the number of listings within the radius boundary.
 17. Themethod of claim 12, further comprising: adjusting the radius boundarybased on a time of day, a day of week or month, a season, or acombination thereof.
 18. The method of claim 12, further comprising:determining a recommended availability time for the parking location;and transmitting the signal including the recommended availability timeto the listing client device.
 19. The method of claim 12, furthercomprising: determining that the number of listings within the radiusboundary is below a listing threshold; and transmitting an alert signalto the listing client device to list the parking location for rent. 20.The method of claim 12, further comprising: determining a recommendedpenalty rate for the parking location, wherein the recommended penaltyrate is charged when a use time of the parking location exceeds areservation time period.
 21. A non-transitory computer-readable mediumhaving stored thereon instructions which, when executed by one or moreprocessors, cause the one or more processors to: receive parkinglocation data relating to a parking location from a listing clientdevice; determine a radius boundary based on the parking location data,wherein the radius boundary is centered on the parking location;determine a number of listings within the radius boundary; determine arecommended listing price for the parking location based on the parkinglocation data and one or more parameters including the number oflistings within the radius boundary; and transmit a signal including therecommended listing price to the listing client device.